From: Michael Albinus Date: Mon, 17 Aug 2020 09:41:46 +0000 (+0200) Subject: ; * doc/lispref/tips.texi: Fix typo. X-Git-Tag: archive/raspbian/1%29.2+1-2+rpi1^2~5^2~16^2~5803 X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:///%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:/?a=commitdiff_plain;h=2b6f52950dbc52f776e065a3716b8bd480d1b922;p=emacs.git ; * doc/lispref/tips.texi: Fix typo. --- diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi index 6292054d306..1826e8f7b42 100644 --- a/doc/lispref/tips.texi +++ b/doc/lispref/tips.texi @@ -956,7 +956,7 @@ multiple sub-sections. Even though that was the only recommended approach for a long time, many people have chosen to use multiple top-level code sections instead. You may chose either style. -Using multiple top-level code sections has the advanatage that it +Using multiple top-level code sections has the advantage that it avoids introducing an additional nesting level but it also means that the section named @samp{Code} does not contain all the code, which is awkward. To avoid that, you should put no code at all inside that